0.0
NA
CVE-2026-24014
Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write
Description

Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to build a file path without sufficient validation. If the internal DataNode RPC port is exposed to an untrusted network, an attacker may use path traversal sequences in the JAR name to write files outside the intended Trigger installation directory. This could allow arbitrary file write with the permissions of the IoTDB process. This issue affects Apache IoTDB: from 1.3.3 before 2.0.8. Users are recommended to upgrade to version 2.0.8, which fixes the issue.

INFO

Published Date :

July 6, 2026, 9:16 a.m.

Last Modified :

July 6, 2026, 9:16 a.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-24014 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Apache iotdb
Solution
Upgrade to Apache IoTDB version 2.0.8 to fix arbitrary file write vulnerability.
  • Upgrade Apache IoTDB to version 2.0.8.
  • Ensure internal RPC ports are not exposed to untrusted networks.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-24014.

URL Resource
https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-24014 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-24014 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-24014 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jul. 06, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'Apache Software Foundation', 'product': 'Apache IoTDB', 'versions': [{'status': 'affected', 'version': '1.3.3', 'lessThan': '2.0.8', 'versionType': 'semver'}], 'defaultStatus': 'unaffected'}]
    Added Description Apache IoTDB DataNode’s internal RPC interface for creating Trigger instances uses the uploaded Trigger JAR name to build a file path without sufficient validation. If the internal DataNode RPC port is exposed to an untrusted network, an attacker may use path traversal sequences in the JAR name to write files outside the intended Trigger installation directory. This could allow arbitrary file write with the permissions of the IoTDB process. This issue affects Apache IoTDB: from 1.3.3 before 2.0.8. Users are recommended to upgrade to version 2.0.8, which fixes the issue.
    Added CWE CWE-284
    Added CWE CWE-434
    Added Reference https://lists.apache.org/thread/38298f803gb5j9nlhf0l9zkf34o90h3m
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.